{\rtf1\ansi\ansicpg1252\cocoartf949\cocoasubrtf540
{\fonttbl\f0\fswiss\fcharset0 Helvetica;}
{\colortbl;\red255\green255\blue255;\red255\green0\blue0;}
\vieww9000\viewh8400\viewkind0
\deftab720
\pard\pardeftab720\qc

\f0\b\fs36 \cf0 Investigation Catalyst Task Rules
\b0\fs24 \
\pard\pardeftab720\ql\qnatural
\cf0 \

\b Acquiring data
\b0 \
	1.  	Everyone and everything has to be someplace, doing something 			during process: track their actions\
	2.  	Force yourself to think "who or what did what when" during process\
	3.  	Look for the actor + actio in observations and data.\
	4.  	Give each actor a name and always use only that name\
	5.  	Give priority to tracking the change makers\
	6.  	Be alert for physical, mental, sensory or "programmer" actions\
	7.  	Break down (decompose) actors or actions to clarfy what happened\
	8.  	Let data, not experience, drive search for data.\
	9.  	Observe the "Do no harm" rule with witnesses and objects\
	10.  	Get permissions before recording witness interviews\
	11.  	Actions change conditions: read conditions to find actions\
	12.  	Quantify actions where possible\
	13.	Build your mental movie frame by frame \
	14.	Get "dids" instead of "did nots"\
\
\

\b Building EBs
\b0 \
	1.  	Transform observed data into actor + action format in EBs\
	2.  	Always record Actor first, then action\
	3.  	Use once pecific and unique name for each actor\
	4.  	NEVER ever put two actors or actions in an EB\
	5.  	Use ? as placeholders until you get needed data\
	6.  	Use glossary for actor and source entries if possible\
	7.  	Avoid poison words like\
		a. pronouns - she, he, tey\
		b. plural nouns - crew, group, squad\
		c. passive voice- was, were,\
		d. conjunctions - and, or, but,\
		e. ambiguous terms, jargon, acronyms\
	8.  Avoid judgmental or opinion words\
		a. inadequate, poorly, faulty - see note A\
		b. did not (implies error, masks proess)\
		c. failed to or violated (accusatory,)\
		d. the cause (ambiguous abstraction)\
		e. root cause (subjective abstraction)\
	9.	Enter a source for every EB\
	10.  	Keep your experience out of EBs\
	11.  	Confirm only observed times: do not confirm estimtes\
\
\

\b Linking EBs
\b0 \
	1.  	Let logic define links: do not assume or guess\
	2.  	Confirm tentative links with data\
	3.  	Strive for black arrowheads used\
\
\

\b Sources
\b0 \
	1.	Cite only sources that can be retrieved or accessed or reproduced\
	2.	Cross-reference any codes sed to identify sources\
	3.	Show more than one source for EB if available\
	4.	Maintain chain of custody for all source objects, documents and 			media used\
\
\

\b Matrixes
\b0 \
	1.  	Review logic flow of EBs on matrix when completed\
	2.  	Have disinterested third party reiew completed matrix for logic flow\
	3.  	Verify accessibility of all sources cited\
	4.  	Explain reason for all remaining ? and gaps (uncertainties)\
	5.  	Remove extraneous EBs and comments to complete matrix\
	6.  	Sign matrix if required.\
\
\

\b Recommendations
\b0 \
	1.  	Examine every EB pair and set, and their links on the matrix for 			options\
	2.  	State pros and cons for making changes proposed\
	3.  	Define how success of change will be identified\
	4.  	Tie all recommendations to an EB, link or EB set.\
	5.  	Don't ask anone to do something you would not want to do yourself\
	6.  	Check carefully for hidden assumptions\
	7.  	Check for unjustified conclusions or arguments\
\

\b Test Plans
\b0 \
	1.  	Whoever Owns the Ball Calls the Game. (If its your money, you are in 		charge!)\
	2.  	\cf2 NO PLAN, NO TESTS!\cf0  (one of the basic commandments for 			Investigation, especially if you own what is to be tested!)\
	3.  	Don't destroy it before you get the data it holds now\
	4.  	Keep Test(s) Relevant. (Get events blocks)\
	5.  	Scale the Plan to the Value of the ata it Will Produce. (Are EBs worth 		cost?)\
	6.  	Progressive destruction demands priorities\
\
\

\fs20 \'a9 2003-2009 Starline Software Ltd (LPGL License)\

\fs24 \
\
\
\
\
}